document how to run tests without venv nor hatch #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Except that when you do this, you aren't testing the verison of bmaptool in this code repo, which IMHO is more confusing than it's worth. I'm fine if that's how you want to test it, but as general instruction it's not a good idea. |
|
Then lets close this! 😉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is possible to run bmaptool and the testsuite without venv, without hatch, without pip and without building and installing anything into venv by just running this:
This assumes that a tool called
bmaptoolis in$PATHand essentially runspython3 -m src.bmaptool.I find this way of running the tests quite a bit easier than going through all the venv, building and installation steps.